View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000602 | T99X171.00 SKB Eagle | SW Issue | public | 2019-04-04 10:17 | 2019-04-17 09:02 |
| Reporter | Assigned To | Due Date | |||
| Priority | high | Severity | s2-severe | Reproducibility | sometimes |
| Status | closed | Resolution | reopened | ||
| Summary | 0000602: There is no response when trying to pair BT via [NUGU] key | ||||
| Description | It has been observed sometimes that there is no response on BT pairing from STB even blinking LED when trying to pair BT via [NUGU] key. [Test Procedure] 1) Make sure that A RCU is in BT connection 2) Trying to pair BT via [NUGU] key with B RCU 3) Verify if BT connection is normally established by B RCU [Actual Result] In step (2), STB never performs any behavior for pairing BT even if LED is blinked. [Expected Result] BT connection must be normally established by B RCU [Version] -. v15.502.8 | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| User List |
(ALTech) Jewoo Lee , (ALTech) SY Yoon , (SW) Jacky Chiang , (SW) Kerwin Chen |
|---|
|
2019-04-04 10:17 developer |
|
|
|
Try 5 times with v15.502.10, no error found. 0. RCU_A paired 1-1. reset RCU_B 1-2. press RCU_B MIC ==> RCU_B paired 1-3. press RCU_A MIC ==> IR data code=d2, map to SKB_FUNC_11(no Action) 2-1. reset RCU_A 2-2. press RCU_A MIC ==> RCU_A paired 2-3. press RCU_B MIC ==> IR data code=d2, map to SKB_FUNC_11(no Action) 3-1. reset RCU_B 3-2. press RCU_B MIC ==> RCU_B paired 3-3. press RCU_A MIC ==> IR data code=d2, map to SKB_FUNC_11(no Action) 4-1. reset RCU_A 4-2. press RCU_A MIC ==> code11 4-3. press RCU_A MIC ==> RCU_A paired 4-4. press RCU_B MIC ==> IR data code=d2, map to SKB_FUNC_11(no Action) 5-1. reset RCU_B 5-2. press RCU_B MIC ==> RCU_B paired 5-3. press RCU_A MIC ==> IR data code=d2, map to SKB_FUNC_11(no Action) |
|
|
0000602:0001975 is A1 chip, test again with A2 chip 0. RCU_A paired 1-1. reset RCU_B 1-2. press RCU_B MIC ==> RCU_B paired 2-1. reset RCU_A 2-2. press RCU_A MIC ==> RCU_A paired 3-1. reset RCU_B 3-2. press RCU_B MIC ==> RCU_B paired 4-1. reset RCU_A 4-2. press RCU_A MIC ==> RCU_A paired 5-1. reset RCU_B 5-2. press RCU_B MIC ==> RCU_B paired 6-1. reset RCU_A 6-2. press RCU_A MIC ==> code11 6-3. press RCU_A MIC ==> RCU_A paired 7-1. reset RCU_B 7-2. press RCU_B MIC ==> RCU_B paired 8-1. reset RCU_A 8-2. press RCU_A MIC ==> RCU_A paired 9-1. reset RCU_B 9-2. press RCU_B MIC ==> code33 9-3. press RCU_B MIC ==> RCU_B paired |
|
|
Hi Eric, I think this issue is not happen on v15.502.10, please verify with it. |
|
|
Hi Jim, The similar issue has been observed in v15.502.10. Could you please check the attached log? The test procedure is as follows. 1) Booting STB 2) STB and RCU are in BT connection state, but no key is operated 3) After unpairing via [*]+[Home], trying to pair BT via [NUGU] key 4) But there is no response after the popup, "trying to connect BT", is displayed 5) Trying [NUGU] key again, but error code 33 is encountered 6) Trying [NUGU] key again and BT connection is OK |
|
|
Hi Eric, In my test, it's total 15 times, 12 times ok. The 3 fails are: 2 code_11 and 1 code_33. The fail rate is similar to "just re-pair using key * and # with only one RCU" And after the 3fails, press MIC again can recover, and I don't see any other issues. In the issue description: "STB never performs any behavior for pairing BT even if LED is blinked." Sorry but please help to convergence issues. For (2), RCU after power off/on or reboot, please go 0000601 For (5), pair fail with code 33, please go 0000533 |
|
|
Hi Jim, Thanks for your feedback. Ok, let's manage these kinds of issues in ID-601 and ID-533. I will close it after verifying it with the next official version. |
|
|
Hi Jim, These kinds of issues have been managed by ID-601 and ID-533, so it closed this case for now. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-04-04 10:17 |
|
New Issue | |
| 2019-04-04 10:17 |
|
Status | new => assigned |
| 2019-04-04 10:17 |
|
Assigned To | => (SW) Kerwin Chen |
| 2019-04-04 10:17 |
|
File Added: log.7z | |
| 2019-04-04 10:17 |
|
File Added: btsnoop_hci.7z | |
| 2019-04-04 10:18 |
|
Issue Monitored: (ALTech) SY Yoon | |
| 2019-04-04 10:18 |
|
Issue Monitored: (SW) Jacky Chiang | |
| 2019-04-04 10:18 |
|
Issue Monitored: (ALTech) Jewoo Lee | |
| 2019-04-09 10:40 | (SW) Jim Chen | Assigned To | (SW) Kerwin Chen => (SW) Jim Chen |
| 2019-04-10 19:05 | (SW) Jim Chen | Note Added: 0001975 | |
| 2019-04-10 19:23 | (SW) Jim Chen | Note Added: 0001976 | |
| 2019-04-10 19:24 | (SW) Jim Chen | Assigned To | (SW) Jim Chen => (ALTech) Eric Kim |
| 2019-04-10 19:24 | (SW) Jim Chen | Status | assigned => resolved |
| 2019-04-10 19:24 | (SW) Jim Chen | Resolution | open => fixed |
| 2019-04-10 19:24 | (SW) Jim Chen | Note Added: 0001977 | |
| 2019-04-11 09:29 |
|
Issue Monitored: (SW) Kerwin Chen | |
| 2019-04-11 09:35 |
|
File Added: log.zip | |
| 2019-04-11 09:35 |
|
Note Added: 0001980 | |
| 2019-04-11 09:36 |
|
Status | resolved => assigned |
| 2019-04-11 09:36 |
|
Resolution | fixed => reopened |
| 2019-04-11 09:36 |
|
Description Updated | |
| 2019-04-11 09:36 |
|
Note Edited: 0001980 | |
| 2019-04-11 09:37 |
|
Assigned To | (ALTech) Eric Kim => (HW) Jim Liang |
| 2019-04-11 10:40 | (SW) Jim Chen | Assigned To | (HW) Jim Liang => (ALTech) Eric Kim |
| 2019-04-11 10:40 | (SW) Jim Chen | Status | assigned => feedback |
| 2019-04-11 10:40 | (SW) Jim Chen | Note Added: 0001982 | |
| 2019-04-11 10:56 |
|
Note Added: 0001985 | |
| 2019-04-11 10:59 |
|
Note Edited: 0001985 | |
| 2019-04-17 09:02 |
|
Status | feedback => closed |
| 2019-04-17 09:02 |
|
Note Added: 0002040 |
